Release 10.1A: OpenEdge Development:
Progress Dynamics Basic Development

Resolving security

Progress Dynamics checks security in this order, from most to least specific:

Progress Dynamics first searches for an allocation against the specified user for the specified login company. If it finds an allocation, Progress Dynamics uses it immediately.
Next, Progress Dynamics searches for an allocation against the specified user in all login companies. If it finds an allocation, Progress Dynamics uses it immediately.
Next, Progress Dynamics checks all groups the user belongs to for any applicable allocation. If Progress Dynamics finds more than one allocation, it applies the cumulative least restrictive security.
Next, Progress Dynamics checks security allocations set up against all users. Within this category, it first checks for allocations against all users within the specified login company. Finally, Progress Dynamics checks allocations against all users for all login companies.
Note: Global security structures and security allocations are cached at session startup. For AppServer sessions, the agents must be trimmed then added back if any global security structures or allocations are added or updated.